fix: escape backticks in generated Go struct tags - #1131

and Go raw literals cannot contain a backtick at all. A column named `bad`tag` therefore closes the literal early and the generated file is not parseable Go, so `gofmt` reports "string literal not terminated".

Go allows a struct tag to be an interpreted literal too, so this switches to that form only when the tag contains a backtick, escaping backslashes and double quotes. Names without a backtick keep the exact raw-literal output they had before, which is what the issue asks for.

There were two identical call sites, one for tables and views and one for composite types. Both now go through the same helper.

Three tests added to the existing `test/server/templates/go.test.ts`, which is a pure unit test file needing no database: a backtick name produces the escaped interpreted literal, a name with a double quote and a backtick escapes both, and an ordinary name still produces the unchanged raw literal. The first two fail without the change and the third passes either way, so the previous output is pinned as well.

`prettier --check` and `tsc -p tsconfig.json --noEmit` are clean.